COMPX375-19B (HAM)

Information Systems Industry Project

15 Points

Edit Header Content
Division of Health Engineering Computing & Science
School of Computing and Mathematical Sciences
Department of Computer Science

Staff

Edit Staff Content

Convenor(s)

Lecturer(s)

Administrator(s)

Placement Coordinator(s)

Tutor(s)

Student Representative(s)

Lab Technician(s)

Librarian(s)

: debby.dada@waikato.ac.nz

You can contact staff by:

  • Calling +64 7 838 4466 select option 1, then enter the extension.
  • Extensions starting with 4, 5, 9 or 3 can also be direct dialled:
    • For extensions starting with 4: dial +64 7 838 extension.
    • For extensions starting with 5: dial +64 7 858 extension.
    • For extensions starting with 9: dial +64 7 837 extension.
    • For extensions starting with 3: dial +64 7 2620 + the last 3 digits of the extension e.g. 3123 = +64 7 262 0123.
Edit Staff Content

Paper Description

Edit Paper Description Content
This project-based paper covers advanced topics in information systems development, while emphasising their application during an actual information systems development project. Students organise themselves into small working groups, then locate an organisation and problem appropriate to address through the development of an information system. During the paper, students will follow the phases and perform the tasks of systems planning, analysis, design and implementation. In doing so, they must submit reports, conduct reviews, demonstrate prototypes developed, and make formal presentations at the appropriate milestones during the semester. The paper will be of interest to those majoring in computer science and information systems and also to students in other Faculties who wish to deepen their understanding of information systems design beyond that covered in COMP219 Database Practice and Experience, and to obtain hands-on experience with these systems in a real business environment.
Edit Paper Description Content

Paper Structure

Edit Paper Structure Content

The lecture hours will mainly be used for discussing advanced themes, methodologies, techniques, and tools for ISD. Lectures are not intended to cover the detailed technical matters that will be required for the production of the reports and prototype; this material has been covered in an introductory way in the prerequisite courses (and students are assumed to possess such knowledge).

You should refer to your previous course notes, the recommended references, and material placed on Moodle. Some of the lectures will give brief reviews or provide you with further information about managing (and surviving!) ISD projects. As third year students we expect you to be able to organise your time effectively, to go and find out information you need if you do not already possess it, and to be able to have reports and other material ready when required.

However, the tutor and I will give you some assistance in doing so during our weekly meetings and whenever you ask for advice or assistance. The focus of this course will be a group project to develop a real-world information system, proceeding from the problem definition stage through to creating a prototype system. Students will work in groups of 4 - 6.

In the first instance, students will form themselves into groups; if necessary, the lecturer will move students between groups or add students to a group sized less than 6 members. Each group will analyse, specify, design, and partially prototype an application system for a local business. The business will be located by the group, and the project will be agreed to by the lecturer.

The project will run according to a strict timetable of deliverable parts of the final report. Effective project management of the systems design study itself, and success in meeting deadlines with professional looking materials and presentations are essential. Draft copies of the appropriate report sections required by the timetable are prepared and presented both in written and oral form by the group to the lecturer, tutors, and the class. Structured walkthroughs are done at all stages to elicit and encourage peer review of the prototypes you develop. While MS Access is provided, the technology used for the prototype is up to the group, but must be demonstrable in presentations and agreed to by the lecturer. Class attendance is expected.

Attendance at group presentations is particularly important; roll will be taken and participation will be part of your grade. The course notes provided are not comprehensive, with additional material covered in class. You are responsible for all material covered in class. Failure to maintain professional behaviour—including attendance at meetings with lecturer and tutor—will result in a loss of course marks. Failure to attend class presentations by student groups will result in a loss of marks.

Edit Paper Structure Content

Learning Outcomes

Edit Learning Outcomes Content

Students who successfully complete the course should be able to:

  • Apply strategies for working effectively in a group
    Linked to the following assessments:
  • Apply appropriate design and development skills to all phases of the software development cycle
    Linked to the following assessments:
  • Demonstrate practical experience in developing for a real-world client
    Linked to the following assessments:
Edit Learning Outcomes Content
Edit Learning Outcomes Content

Assessment

Edit Assessments Content

Assessment Components

Edit Assessments Content

The internal assessment/exam ratio (as stated in the University Calendar) is 100:0. There is no final exam. The final exam makes up 0% of the overall mark.

The internal assessment/exam ratio (as stated in the University Calendar) is 100:0 or 0:0, whichever is more favourable for the student. The final exam makes up either 0% or 0% of the overall mark.

Component DescriptionDue Date TimePercentage of overall markSubmission MethodCompulsory
1. Memorandum of Understanding
0
  • Other:
2. Information System Proposal
15
  • Other: Upload to Moodle
3. Structured Requirements report
15
  • Other: Upload to Moodle
4. Interface Design and Testing Schedule
10
  • Other: Upload to Moodle
5. Database design report
10
  • Other: Upload to Moodle
6. Final project report & client feedback
25
  • Other: Upload to Moodle
7. Individual Use Case assessment
5
  • Hand-in: In Lecture
8. Individual in-class presentation
5
9. User Interface critique report
5
  • Hand-in: In Lecture
10. Individual marks for professional behavior
10
Assessment Total:     100    
Failing to complete a compulsory assessment component of a paper will result in an IC grade
Edit Assessments Content

Required and Recommended Readings

Edit Required Readings Content

Recommended Readings

Edit Recommended Readings Content

Brooks, F.P. The Mythical Man-Month: Essays on Software Engineering, Addison-Wesley, 1975.

Phillips, D. The Software Project Manager’s Handbook: Principles that Work at Work. IEEE Computer Society Press, 1998.

Sides, C.H. How to write and present technical information, Oryx Press, 1991.

Edit Recommended Readings Content

Other Resources

Edit Other Resources Content
Hoffer, J., et al Modern Systems Analysis and Design. (3nd edition) Prentice-Hall, 2015.
Edit Other Resources Content

Online Support

Edit Online Support Content
Additional suggested readings will be posted  on Moodle, as will lecture notes (if available),  assessment descriptions and rubrics.
Edit Online Support Content

Workload

Edit Workload Content
On average you should expect to spend about 12 hours per week on this class. This figure includes lectures, reading, assignments, meetings, and system development.
Edit Workload Content

Linkages to Other Papers

Edit Linkages Content

Prerequisite(s)

Prerequisite papers: COMP219 or COMPX223

Corequisite(s)

Equivalent(s)

Restriction(s)

Restricted papers: COMP314, COMP315, and COMPX374

Edit Linkages Content